EVE Search - I keep crashing/logging out.

Check My IP Information

All Channels

Issues, Workarounds & Localization

I keep crashing/logging out.

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]


Author	Thread Statistics \| Show CCP posts - 3 post(s)
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.12 22:42:00 - [1] - Quote Had very few disconnects from the EVE client for the year that I have been playing. All of a sudden since the 12 April patch I disconnected 3 times in a couple hours. Aus player here.
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.13 10:12:00 - [2] - Quote This was the situation during normal operation: Quote: Pinging 87.237.38.200 with 32 bytes of data: Reply from 87.237.38.200: bytes=32 time=291ms TTL=116 Reply from 87.237.38.200: bytes=32 time=291ms TTL=116 Reply from 87.237.38.200: bytes=32 time=291ms TTL=116 Reply from 87.237.38.200: bytes=32 time=291ms TTL=116 Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 291ms, Maximum = 291ms, Average = 291ms tracert 87.237.38.200 Tracing route to srv200-g.ccp.cc [87.237.38.200] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 14 ms 14 ms 14 ms nexthop.wa.iinet.net.au [203.215.5.243] 3 14 ms 14 ms 13 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20] 4 62 ms 62 ms 62 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20] 5 61 ms 63 ms 62 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137] 6 65 ms 64 ms 62 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18] 7 64 ms 88 ms 65 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102] 8 63 ms 60 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45] 9 65 ms 65 ms 65 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1] 10 202 ms 202 ms 202 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146] 11 249 ms 250 ms 249 ms i-3-4.eqla01.bi.reach.com [202.84.251.154] 12 288 ms 272 ms 298 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202] 13 291 ms 291 ms 299 ms 204.245.39.42 14 291 ms 291 ms 291 ms srv245-e.ccp.cc [87.237.36.245] 15 291 ms 291 ms 291 ms srv248-e.ccp.cc [87.237.36.248] 16 292 ms 291 ms 292 ms srv200-g.ccp.cc [87.237.38.200] Trace complete. Then I was dumped from the client and pinged with the following result: Quote: ping 87.237.38.200 Pinging 87.237.38.200 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Reply from 87.237.38.200: bytes=32 time=292ms TTL=116 Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 292ms, Maximum = 292ms, Average = 292ms And later dumped again and attempted tracert immediately and was greeted with: Quote: Tracing route to srv200-g.ccp.cc [87.237.38.200] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 13 ms 13 ms 13 ms nexthop.wa.iinet.net.au [203.215.5.243] 3 14 ms 14 ms 14 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20] 4 62 ms 62 ms 62 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20] 5 62 ms 62 ms 62 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137] 6 61 ms 62 ms 62 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18] 7 106 ms 64 ms 64 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102] 8 60 ms 60 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45] 9 65 ms 65 ms 65 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1] 10 203 ms 202 ms 202 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146] 11 250 ms 249 ms 249 ms i-3-4.eqla01.bi.reach.com [202.84.251.154] 12 274 ms 275 ms 273 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202] 13 * * 299 ms 204.245.39.42 14 296 ms 477 ms 399 ms srv245-e.ccp.cc [87.237.36.245] 15 296 ms 296 ms 300 ms srv248-e.ccp.cc [87.237.36.248] 16 296 ms 296 ms 296 ms srv200-g.ccp.cc [87.237.38.200] Trace complete. Hope this helps identify the problem. Issue wit the onnection to 204.245.39.42?
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.13 22:57:00 - [3] - Quote Reading through the thread it appears that whatever was changed on Thursday (EVE time) which was Friday morning when I patched, seems coincidently to have resulted in a few Aussie players posting that they have this issue. I applied the last patch Friday morning and the disconnects started happening at a rate of at least 1-2 per hour. Is CCP going to revert/fix the Thursday change or we Aussies just going to have to fork out for third party software to make EVE work?
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.14 01:23:00 - [4] - Quote Unfortunately 204.245.39.42 seems to be the one causing my issues, and I suspect issues for other Aussie players above. I wish to know whether the change implemented by CCP Mort is encouraging our packets to go through this dodgy server. Sorry I am not techie enough to know the correct terminology, but from several tracert's I have run, they all seem to hang at that point longer than all the other jumps. As mentioned before, I almost never had unexplained drops in a year of playing, and now they are happening regularly to the point of making EVE unplayable.
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.15 08:06:00 - [5] - Quote So many dropouts today ... rapidly approaching ragequit. What is the point of an "Issues" forum if CCP is largely deaf to the issues? Is there a better way to raise this problem?
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.16 08:54:00 - [6] - Quote Holy f-balls what have you guys done... EVE is now officially unplayabale: Quote: Tracing route to srv200-g.ccp.cc [87.237.38.200] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 39 ms 27 ms 19 ms nexthop.wa.iinet.net.au [203.215.5.243] 3 50 ms 127 ms 104 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20] 4 128 ms 128 ms 135 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20] 5 122 ms 144 ms 220 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137] 6 85 ms 126 ms 77 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18] 7 158 ms 152 ms 69 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102] 8 114 ms 118 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45] 9 171 ms 148 ms 101 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1] 10 251 ms 220 ms 320 ms i-0-6-2-0.eqnx-core01.bx.reach.com [202.84.144.185] 11 293 ms 294 ms 293 ms i-2-3.eig-core01.bi.reach.com [202.84.141.161] 12 595 ms 330 ms 365 ms i-2-0-0.nwk-core01.bi.reach.com [202.84.141.90] 13 2908 ms * 2871 ms i-4-1.ulco-core01.bx.reach.com [202.84.144.86] 14 2990 ms 3215 ms 3189 ms ldn-s2-rou-1041.UK.eurorings.net [195.66.224.54] 15 3022 ms 3051 ms * 134.222.109.115 16 * 2938 ms 3035 ms srv248-e.ccp.cc [87.237.36.248] 17 * 2969 ms 2911 ms srv200-g.ccp.cc [87.237.38.200] Trace complete. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Pinging 87.237.38.200 with 32 bytes of data: Request timed out. Request timed out. Reply from 87.237.38.200: bytes=32 time=2945ms TTL=116 Reply from 87.237.38.200: bytes=32 time=2902ms TTL=116 Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 2902ms, Maximum = 2945ms, Average = 2923ms Route changed and impossible to play on.
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.17 22:35:00 - [7] - Quote Been running sans Battleping for a couple of hours, and despite going through the ebil 204.245.38.42 the game seems to be holding up, 300-400 pings notwithstanding, but that's pretty much par for the course in Perth, Australia. Will keep an eye on the situation. Would be good to know whether CCP did anything or whether this is just dumb luck.
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.20 09:04:00 - [8] - Quote Problem is back gain ... Battleping will expire in a few days and so will my subs to EVE if the problem persists. I also note 204.245.39.42 is in the route again.
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.23 22:16:00 - [9] - Quote OK Well Battleping free trial expired and problem persisting so CCP is not getting anymore dollars from me. So long and thanks for all the fish.
Linolea Austrene Hidden Agenda Deep Space Engineering 0	Posted - 2012.04.24 21:20:00 - [10] - Quote Xapp Branigan wrote: I am with iinet in Australia they can't do anything. If everyone getting this issue hassle this company perhaps we might get some results. It would make more sense if the entity with the vested interest (i.e. CCP making money, or losing it in this case) approach the company in question. Judging by the complete lack of engagement of CCP in this thread, I assume it is not affecting enough people for them to care. I find this particularly galling as my problems started after CCP Mort said he tweaked routing on page 3 of this thread, and then seemingly walked away from the issue. Removing subs is the only language gaming companies seem to understand. Just a "we are working on it" would be helpful.

Copyright © 2006-2025, Chribba - OMG Labs. All Rights Reserved. - perf 0,06s, ref 20250718/1310
EVE-Online™ and Eve imagery © CCP.

bitcoin: 1CHRiBBArqpw5Yz7x5KS2RRtN5ubEn5gF

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.